Remotely alerting a wireless device

ABSTRACT

A wireless device may be alerted. For example, a message may be received from an invoking party and parsed for request data. Then a determination may be made as to whether identification data in the received message matches identification data resident in the wireless device. Next, the wireless device may be alerted when the received identification data matches the identification data resident in the wireless device and when the request data includes a request to alert the wireless device. A return message may be sent to the invoking party when the request data includes the request to alert the wireless device. The return message may indicate that the wireless device as been alerted. Alerting the wireless device may comprise causing the wireless device to perform a function configured to indicate to a subject that the wireless device has been lost.

RELATED APPLICATIONS

This patent application is a continuation-in-part of U.S. patentapplication Ser. No. 10/881,669, entitled “System And Methods ForRemotely Recovering And Purging Data From A Wireless Device In ACommunications Network,” filed on Jun. 30, 2004 and assigned to the sameassignee as this application. The aforementioned patent application isexpressly incorporated herein by reference. Furthermore, this patentapplication is related to U.S. patent application Ser. No. 11/197,844,entitled “Methods And Systems For Remotely Recovering Security Data In AWireless Device In A Communications Network,” filed Aug. 5, 2005,assigned to the assignee of the present patent application and isexpressly incorporated herein by reference.

BACKGROUND

Wireless devices for communicating and storing voice and data arebecoming commonplace. Users of wireless communication devices areincreasingly using their wireless devices to send electronic mail(“E-mail”) as well as store personal data, such as contact lists,calendar information, to do lists, and other notes. Much of this datamay be considered as private to a user (e.g., passwords, credit card orbank account numbers, telephone numbers, addresses, and calendar orschedule information. Undesirable consequences may result for the userif the wireless device is lost and falls into the wrong hands.

Many wireless communication devices permit the user to enable a softwarelock of the device, which prevents use of the device unless a passwordis entered, and thus protects user data. However, use of this lockingfeature typically requires additional steps that the user mightotherwise not wish to take in operating their device, such asremembering and entering a multi-digit code every time the device isturned on or when an attempt is made to access the user's private data.As a result, the wireless device's locking feature is frequently unused.Moreover, if a device is stolen or lost, even if the locking feature isin place, the user suffers the inconvenience of losing his or her dataand wondering if the device had been previously locked.

SUMMARY OF THE INVENTION

Consistent with embodiments of the present invention, systems andmethods are disclosed for alerting a wireless device.

For example, a message may be received from an invoking party and parsedfor request data. Then a determination may be made as to whetheridentification data in the received message matches identification dataresident in the wireless device. Next, the wireless device may bealerted when the received identification data matches the identificationdata resident in the wireless device and when the request data includesa request to alert the wireless device. A return message may be sent tothe invoking party when the request data includes the request to alertthe wireless device. The return message may indicate that the wirelessdevice as been alerted. Alerting the wireless device may comprisecausing the wireless device to perform a function configured to indicateto a subject that the wireless device has been lost or mislaid.

It is to be understood that both the foregoing general description andthe following detailed description are examples and should not beconsidered to restrict the invention's scope, as described and claimed.Further, features and/or variations may be provided in addition to thoseset forth herein. For example, embodiments of the invention may bedirected to various feature combinations and sub-combinations describedin the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentinvention. In the drawings:

FIG. 1 is a network diagram illustrating aspects of a datacommunications network;

FIG. 2 is a network diagram illustrating aspects of a voicecommunications network;

FIG. 3A is a flow diagram illustrating aspects of a process forrecovering data, purging data, and performing other operations withrespect to a wireless device in the data communications network of FIG.1;

FIG. 3B is a flow diagram continuing the process of FIG. 3A;

FIG. 4A is a flow diagram illustrating aspects of a process forrecovering data, purging data, and performing other operations withrespect to a wireless device in the voice communications network of FIG.2; and

FIG. 4B is a flow diagram continuing the process of FIG. 4A.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the invention may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe invention. Instead, the proper scope of the invention is defined bythe appended claims.

Systems and methods for remotely recovering data from a wireless device,purging data from the wireless device, and alerting a wireless devicemay be provided. A data message containing instructions forrecovering/purging data stored on the device may be sent to the wirelessdevice. The data message may be received by a recovery/purge applicationresident on the wireless device. FIGS. 1 and 2 and the correspondingdiscussion are intended to provide a brief, general description of asuitable communications network environment consistent with embodimentsof the invention.

Referring now to FIG. 1, a data communications network for performingembodiments of the invention will be described. As shown in FIG. 1, acommunications network 100 includes communications devices 102 forsending and receiving data over a network 114. Communications devices102 include, for example, a wireless hand-held computer 104 and apersonal computer 106. According to embodiments of the invention,wireless hand-held computer 104 utilizes a wireless data gateway 108 tosend and receive data messages over the network 114. As will bedescribed in greater detail below, communications devices 102 may beutilized to send data messages over network 114 to recover and/or purgemessages from lost or stolen devices in communications network 100. Thedata messages may include, for instance, electronic mail (“e-mail”)messages, short message service (“SMS”) messages, text messages, or anyother message types that may be communicated in a communicationsnetwork. Embodiments of the invention are not limited to hand-heldcomputer 104 or personal computer 106, but may be practiced with othercommunications devices including, but not limited to, two-way pagingdevices, voice over Internet protocol (“VOIP”) or Internet telephones,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like.

Network 114 interconnects communications devices 102 with a networkserver computer 112 for managing data traffic and a web server computer126 for delivering web pages to connected devices over the network 114.Network 114 may include any type of computing network, including a localarea network or a wide area network, such as the Internet. Network 114provides a medium for enabling communication between communicationsdevices 102, server computers 112 and 126, a computer 110, and awireless device 118.

Wireless device 118 may be a hand-held computer. Wireless device 118sends and receives data messages over the network 114 throughcommunication with wireless data gateways 108 and 116. Wireless datagateways 108 and 116 convert data communicated over a wireless datanetwork (not shown) so that it may be communicated over network 114.

Consistent with embodiments of the invention, wireless device 118 mayfurther include “smart phone” functionality. Smart phones combine thefunctions of a conventional mobile phone with functionality typicallyincluded in a personal or hand-held computer. This functionalityincludes the capability of saving data, executing software programs,sending and receiving e-mail and instant messages, and accessing Webpages over the Internet.

Wireless device 118 is operative to execute a data recovery/purgeapplication 124. According to illustrative embodiments of the invention,data recovery/purge application 124 may be utilized to recover and/orpurge saved data from wireless device 118, e.g., upon the devicebecoming lost or stolen. Data recovery/purge application 124 may beexecuted or invoked upon receiving a message from either of thecommunications devices 102. The message may contain request data foridentifying a lost wireless device, recovering the saved data, purgingthe saved data, recovering and then purging the saved data, alertingwireless device 118 or other instructions. The request data may alsocontain a return address, such as an e-mail address, for sending therecovered data and/or confirmation of a data purge to wireless devices102 or to computer 110. The functions of data recovery/purge application124 will be discussed in greater detail below with reference to FIGS. 3and 4.

Referring now to FIG. 2, a voice communications network for performingembodiments of the invention will be described. As shown in FIG. 2, acommunications network 200 includes communications devices 202 forconducting voice and data communications with a switch 230.Communications devices 202 may include a standard wireline telephone set206 which is connected via a subscriber line to switch 230.Communications devices 202 also include a wireless telephone 204 that isin wireless communication with a mobile switching center (“MSC”) 208.MSC 208 may be utilized to communicate the wireless voice traffic frommobile telephone 204 to switch 230 via a wireline connection. Switch230, MSC 208 and the connections between them and communications devices202 may be components in a typical public switched telephone network(“PSTN”). According to embodiments of the invention, switch 230 may be astandard central office circuit switch or a softswitch for routing voiceand data traffic in the PSTN.

Communications network 200 also includes a voice node 219 incommunication with switch 230 and a customer profile database 226.According to embodiments of the invention, voice node 219 may be aserver computer with interactive voice response (“IVR”) functionality.For instance, a customer may utilize an IVR to retrieve up-to-dateaccount information from a bank by entering his or her account number ona touch-tone telephone keypad in response to a synthesized voicerecording. The IVR will then access a database associated with the bankand retrieve account information associated with the customer's accountnumber. The account information may then be presented to the customerover the telephone via a synthesized voice generated by the IVR.

Communications network 200 also includes a network 214. Network 214provides a medium for enabling communication between voice node 219, acomputer 210, and wireless device 218. The communication with wirelessdevice 218 may be enabled through a wireless data gateway 216 thatconverts data communicated over network 214 so that it is compatiblewith a wireless data network (not shown) in communication with wirelessdevice 218. Network 214 may include any type of computing network,including a local area network or a wide area network, such as theInternet.

Voice node 219 is operative to execute a data recovery/purge applicationprogram 224 and an e-mail server program 228. According to embodimentsof the invention, voice node 219 may be utilized to receive a voice callto a special directory number from switch 230 for locating a lost orstolen wireless device in communications network 200. Datarecovery/purge application 224 may be executed or invoked upon voicenode 219 retrieving information from database 226 associated with awireless directory number for the lost or stolen wireless device. Datarecovery/purge application 224 may receive this information and composea message to send to e-mail server program 228 that then sends themessage over network 214 to a copy of data recovery/purge application224 executed on wireless device 218. As previously discussed withrespect to wireless device 118 in the description of FIG. 1, wirelessdevice 218 may include smart phone functionality to enable the executionof data recovery/purge application 224 as well as other softwareapplication programs.

The message may contain request data for identifying the wirelessdevice, recovering data saved on the wireless devices, purging the saveddata, recovering and then purging the saved data, or other instructions.The request data may also contain a return address, such as an e-mailaddress, for sending the recovered data and/or confirmation of a datapurge to computer 210. The functions of data recovery/purge application224 in communications network 200 will be discussed in greater detailbelow with reference to FIGS. 4A and 4B.

Referring now to FIG. 3A, a routine 300 will be described illustrating aprocess that may be performed by data recovery/purge application 124 forrecovering data, purging data, and alerting wireless device 118performing other operations with respect to wireless device 118 incommunications network 100, discussed above. The logical operations ofvarious embodiments of the present invention may be implemented (1) as asequence of computer implemented acts or program modules running on acomputing system and/or (2) as interconnected machine logic circuits orcircuit modules within the computing system. Accordingly, the logicaloperations illustrated in FIGS. 3A-4B, and making up the embodiments ofthe present invention described herein are referred to variously asoperations, structural devices, acts, or modules. These operations,structural devices, acts, and modules may be implemented in software, infirmware, in special purpose digital logic, and any combination thereof.

Routine 300 begins at operation 305, wherein a user/invoking party ofcommunications devices 102 initiates a message to execute datarecovery/purge application 124 resident in wireless device 118. Inparticular, an invoking party in communications network 100 may initiatea message by sending an e-mail message from hand-held computer 104 orthe computer 106 directly to wireless device 118 over network 114. Thee-mail message may include a form comprising a number of fields ofrequest data which are parsed by data recovery/purge application 124upon receipt of the message. The request data fields may include a keyfield indicating a unique identification (such as the wireless telephonenumber) of the wireless device being contacted, a request type fieldindicating the type of operation to be performed by recovery/data purgeapplication 124, and a data recovery address which may be an e-mailaddress for sending recovered data, a purge confirmation, or other datato the invoking party. The message is not limited to an e-mail messagebut may also take the form of wireless text messages such as SMSmessages in addition to various other types of wireless and wirelinemessaging known.

From operation 305, routine 300 continues to operation 310 where themessage from the invoking party is received at wireless device 118 atwhich time data recovery/purge application 124 is executed. Forinstance, wireless device 118 may be preconfigured (i.e., preprogrammed)to automatically execute data recovery/purge application 124 each timean e-mail message is received. Once executed data recovery/purgeapplication 124 determines if the received message includes request dataas described in detail at operation 315.

From operation 310, routine 300 continues to operation 315 where datarecovery/purge application 124 parses the received message from theinvoking party for request data indicating a request to recover data,purge data, or to perform other operations with respect to wirelessdevice 118. In particular, recovery/purge application 124 may beconfigured to search for request data fields in an e-mail message sentby the invoking party. For instance, recovery/purge application 124 mayinitially search for the key field to confirm that the request data inthe message is applicable to wireless device 118.

From operation 315, routine 300 continues to operation 320 where datarecovery/purge application 124 compares identification information inthe request data to identification data previously stored in wirelessdevice 118. In particular, recovery/purge application 124 may search foran identification number in the key field in the request data. Theidentification number may include, for instance, the wireless telephonenumber of wireless device 118.

If, at operation 320, recovery/purge application 124 determines that theidentification data does not match the identification data stored inwireless device 118, routine 300 branches to operation 310 whererecovery/purge application 124 waits to receive another message from theinvoking party. Upon determining a non-match of the identification data,recovery/purge application 124 may further be configured to generate analert in a return message to the invoking party indicating that the sentidentification data does not match the identification data in thewireless device 118.

If, at operation 320, recovery/purge application 124 determines that theidentification data matches the identification data stored in wirelessdevice 118, routine 300 continues to operation 330. At operation 330,recovery/purge application 124 determines the type of request containedin the request data in the received message from the invoking party. Forinstance, recovery/purge application 124 may search a request type fieldin the received message to identify whether a request was made torecover personal contact data stored in wireless device 118. It shouldbe noted that multiple types of requests can be requested. For example,the request data can indicate that Lock, Locate, and Alert, or any likecombination of more than one of the types of request described hereinand in FIGS. 3A, 3B, 4A and 4B.

From operation 330, routine 300 continues to operation 335 where datarecovery/purge application 124 determines whether the request dataincludes a request to recover the data stored in wireless device 118. Ifthe request data includes a request to recover the data stored inwireless device 118, routine 300 continues to operation 340 where datarecovery/purge application 124 retrieves the data stored in wirelessdevice 118. In particular, data recovery/purge application 124 mayaccess the memory in wireless device 118 and initiate commands to make acopy of the stored data. For instance, data recovery/purge application124 may be configured to copy a user's personal data, such as telephoneand address data, calendar information, passwords, and account numbersfrom wireless device 118 into a data file. Routine 300 then continues tooperation 345.

If, at operation 335, recovery/purge application 124 determines that therequest data does not include a request to recover the data stored inwireless device 118, routine 300 continues to operation 345 whererecovery/purge application 124 determines whether the request dataincludes a request to purge the data stored in wireless device 118. Ifthe request data includes a request to purge the data stored in wirelessdevice 118, routine 300 continues to operation 350 where recovery/purgeapplication 124 purges data stored in wireless device 118. Inparticular, data recovery/purge application 124 may execute a deletecommand from a menu in wireless device 118 to purge the stored data.Routine 300 then continues to off-page connector A where routine 300continues in FIG. 3B. If, at operation 335, recovery/purge application124 determines that the request data does not include a request to purgethe data stored in wireless device 118, routine 300 continues tooff-page connector A where routine 300 continues in FIG. 3B.

Referring now to FIG. 3B, routine 300 continues from off-page connectorA to operation 355 where data recovery/purge application 124 determineswhether the request data includes a request to lock wireless device 118.If the request data includes a request to lock wireless device 118,routine 300 continues to operation 360 where data recovery/purgeapplication 124 locks wireless device 118. In particular, datarecovery/purge application 124 may access a menu in wireless device 118and enter a numerical code, provided by the invoking party in therequest data, to lock the device so that device functions and data areprevented from being accessed by an unknown party. Routine 300 thencontinues to operation 365.

If the request data does not include a request to lock the wirelessdevice 118, routine 300 continues to operation 365 where datarecovery/purge application 124 determines whether the request dataincludes a request to locate wireless device 118. If the request dataincludes a request to locate wireless device 118, routine 300 continuesto operation 370 where data recovery/purge application 124 executing onwireless device 118 retrieves location information. In particular, datarecovery/purge application 124, in response to receiving a request forlocation information, may be configured to access a menu in wirelessdevice 118 to retrieve location data such as Global Positioning System(“GPS”) data (if the wireless device 118 includes this feature). Routine300 then continues to operation 375.

If the request data does not include a request to lock wireless device118, routine 300 continues to operation 375 where data recovery/purgeapplication 124 sends a return message to the invoking party. Inparticular, data recovery/purge application 124 may initiate and send ane-mail message from wireless device 118 over network 114 to a datarecovery address or addresses specified in the request data sent by theinvoking party. The return address may be a different address than theone from which the request data was sent by the invoking party. Forinstance, the invoking party may have initiated a recovery and purgerequest from computer 106 (which may be a home computer) but may wishthe recovered data to be sent to an e-mail address associated with thecomputer 110 (which may be a work computer). In addition, the returnmessage may be sent to multiple addresses.

The return message may include the recovered data file as an attachmentand an acknowledgement confirming that data was recovered and/or purgedfrom wireless device 118. In one illustrative embodiment, datarecovery/purge application 124 may be configured to retry a datarecovery or purge request until successful. The return message may alsoinclude other information requested by the invoking party such as aconfirmation that wireless device 118 was locked or current locationinformation for wireless device 118. From operation 375, routine 300continues to operation 380, where it ends.

Turning now to FIG. 4A, a routine 400 will be described illustrating aprocess that may be performed by data recovery/purge application 224 forrecovering data, purging data, and performing other operations withrespect to wireless devices 218 in communications network 200, discussedabove. Routine 400 begins at operation 402, wherein a user/invokingparty of communications devices 202 initiates a message request toexecute data recovery/purge application 224 resident in wireless device218. In particular, an invoking party in communications network 200 mayinitiate a message request by making a voice call to voice node 219.Upon the completion of the call, voice node 219 may generate synthesizedvoice prompts requesting the telephone number of wireless device 218 andthe type of request or requests (e.g., data recovery, data purge, devicelock, or device location). Once this information is received, voice node219 accesses database 226 to retrieve profile information which mayinclude identification data associated with wireless device 218 and areturn address to be included in request data received by datarecovery/purge application 224.

From operation 402, routine 400 continues to operation 404 where voicenode 219 executes data recovery/purge application 224 that receives therequest data stored in the database and provided by the invoking party.In particular, data recovery/purge application 224 receives theidentification data, the return address, and the request type (or types)for generating a message to send to wireless device 218.

From operation 404, routine 400 continues to operation 405 whererecovery/purge application 224 executing in voice node 219 generates amessage to execute data recovery/purge application 224 resident inwireless device 218. In particular, data recovery/purge application 224in the voice node may generate an e-mail message that e-mail serverprogram 228 sends directly to wireless device 218 over network 214. Asdiscussed above in the description of FIG. 3A, the e-mail message mayinclude a form comprising a number of fields of request data including akey field indicating a unique identification (such as the wirelesstelephone number) of the wireless device being contacted, a request typefield indicating the type of operation to be performed by recovery/datapurge application 224 resident in wireless device 218, and a datarecovery address which may be an e-mail address for sending recovereddata, a purge confirmation, or other data to the invoking party.Alternatively, the message may also take the form of a wireless textmessage such as an SMS messages in addition to various other types ofwireless and wireline messaging known to those skilled in the art.

From operation 405, routine 400 continues to operation 410 where themessage from the invoking party is received at the wireless device 218at which time data recovery/purge application 224 resident in wirelessdevice 218 is executed. For instance, wireless device 218 may bepreconfigured (i.e., preprogrammed) to automatically execute datarecovery/purge application 224 each time an e-mail message is received.Once executed data recovery/purge application 224 determines if thereceived message includes request data as described in detail atoperation 415.

From operation 410, routine 400 continues to operation 415 where datarecovery/purge application 224 parses the received message from theinvoking party for request data indicating a request to recover data,purge data, or to perform other operations with respect to wirelessdevice 218. In particular, recovery/purge application 224 may beconfigured to search for request data fields in an e-mail message. Forinstance, recovery/purge application 224 may initially search for thekey field to confirm that the request data in the message is applicableto wireless telephone device 218.

From operation 415, routine 400 continues to operation 420 where datarecovery/purge application 224 compares identification information inthe request data to identification data previously stored in wirelessdevice 218. In particular, recovery/purge application 224 may search foran identification number in the key field in the request data. Theidentification number may include, for instance, the wireless telephonenumber of wireless device 218.

If, at operation 420, recovery/purge application 224 determines that theidentification data does not match the identification data stored inwireless device 218, routine 400 branches to operation 410 whererecovery/purge application 224 waits to receive another message. Upondetermining a non-match of the identification data, recovery/purgeapplication 224 may further be configured to generate an alert in areturn message to computer 210 associated with the invoking partyindicating that the sent identification data does not match theidentification data in wireless device 218.

If, at operation 420, recovery/purge application 224 determines that theidentification data matches the identification data stored in wirelessdevice 218, routine 400 continues to operation 430. At operation 430,recovery/purge application 224 determines the type of request containedin the request data in the received message from the invoking party. Forinstance, recovery/purge application 224 may search a request type fieldin the received message to identify whether a request was made torecover personal contact data stored in wireless device 218.

From operation 430, routine 400 continues to operation 435 where datarecovery/purge application 224 determines whether the request dataincludes a request to recover the data stored in wireless device 218. Ifthe request data includes a request to recover the data stored inwireless device 218, routine 400 continues to operation 440 where datarecovery/purge application 224 retrieves data stored in the wirelessdevice 218. In particular, data recovery/purge application 224 mayaccess the memory in wireless device 218 and initiate commands to make acopy of the stored data. For instance, data recovery/purge application224 may be configured to copy a user's personal data, such as telephoneand address data, calendar information, passwords, and account numbersfrom wireless device 218 into a data file. Routine 400 then continues tooperation 445.

If, at operation 435, recovery/purge application 224 determines that therequest data does not include a request to recover the data stored inwireless device 218, routine 400 continues to operation 445 whererecovery/purge application 224 determines whether the request dataincludes a request to purge the data stored in wireless device 218. Ifthe request data includes a request to purge the data stored in wirelessdevice 218, routine 400 continues to operation 450 where recovery/purgeapplication 224 purges data stored in wireless device 218. Inparticular, data recovery/purge application 224 may execute a deletecommand from a menu in wireless device 218 to purge the stored data.Routine 400 then continues to off-page connector A where the routine 400continues in FIG. 4B. If, at operation 435, recovery/purge application224 determines that the request data does not include a request to purgethe data stored in wireless device 218, routine 400 continues tooff-page connector A where routine 400 continues in FIG. 4B.

Referring now to FIG. 4B, routine 400 continues from off-page connectorA to operation 455 where data recovery/purge application 224 determineswhether the request data includes a request to lock wireless device 218.If the request data includes a request to lock wireless device 218,routine 400 continues to operation 460 where data recovery/purgeapplication 224 locks wireless device 218. In particular, datarecovery/purge application 224 may access a menu in wireless device 218and enter a numerical code, provided by the invoking party in therequest data, to lock the device so that device functions and data areprevented from being accessed by an unknown party. Routine 400 thencontinues to operation 465.

If the request data does not include a request to lock the wirelessdevice 218, routine 400 continues to operation 465 where datarecovery/purge application 224 determines whether the request dataincludes a request to locate wireless device 218. If the request dataincludes a request to locate the wireless device 218, routine 400continues to operation 470 where data recovery/purge application 224executing on wireless device 218 retrieves location information. Inparticular, data recovery/purge application 224, in response toreceiving a request for location information, may be configured toaccess a menu in wireless device 218 to retrieve location data, such asGlobal Positioning System (“GPS”) data (if the wireless device 218includes this feature).

If the request data does not include a request to locate wireless device218, routine 400 continues to operation 475 where data recovery/purgeapplication 224 determines whether the request data includes a requestto perform an alert task via wireless device 218. If the request dataincludes a request to perform an alert task via wireless device 218,routine 400 continues to operation 480 where data recovery/purgeapplication 224 executing on wireless device 218 causes wireless device218 to perform a function configured to indicate to a subject thatwireless device 218 has been lost. In particular, data recovery/purgeapplication 224, in response to receiving an alert request, may beconfigured to cause wireless device 218 to produce a visible alert onwireless device 218. For example, in response to data recovery/purgeapplication 224, wireless device 218 may flash a light on wirelessdevice 218. The flashing may be in some distinguishable sequence ofon/off time segments or may be a distinguishable light color. Thevisible alert may be displayed via any visible component enabled bydevice 218. For example, if device 218 includes a display screen, thealert may be produced by a display presented for visual viewing on thescreen. In other words the visible alert on wireless device 218 flashingmay indicate to the subject (e.g., a person who may have noticed orfound wireless device 218) that wireless device 218 is considered lostor mislaid by its owner. The visible alert may be presented in anymanner to indicate that wireless device 218 is considered lost by itsowner.

Moreover, data recovery/purge application 224, in response to receivingthe alert request, may be configured to cause wireless device 218 toemit an audible alert (e.g. a tone) from wireless device 218. Theaudible alert may be loaded into wireless device 218 in the same waythat a ring tone or other audible alert is loaded. For example, theaudible alert may be pre-established on wireless device 218 prior towireless device 218 being alerted, provided to wireless device 218 whenwireless device 218 is alerted, or provided to wireless device 218 afterwireless device 218 is alerted. In other words, the type of audiblealert to be sounded in response to the alert request may bepre-established and pre-loaded into wireless device 218. In otherembodiments of the invention, the type of audible alert to be sounded inresponse to the alert request may be received with the alert request orsubsequent to receiving the alert request. Like the visible alert andaudible alert, the alert may also be presented in the form of a motionalert produced by the device, for example, a vibration.

Furthermore, data recovery/purge application 224, in response toreceiving an alert request, may be configured to cause wireless device218 to display a message on wireless device 218. Like the aforementionedaudible alert, the displayed message may be pre-established on wirelessdevice 218 prior to wireless device 218 being alerted, provided towireless device 218 when wireless device 218 is alerted, or provided towireless device 218 after the wireless is alerted. In other words, themessage to be displayed in response to the alert request may bepre-established and pre-loaded into wireless device 218. In otherembodiments, the message to be displayed in response to the alertrequest may be received with the alert request or subsequent toreceiving the alert request. The message may comprise, for example,information configured to let a subject finding wireless device 218 knowthat wireless device 218 is lost and may provide directions on how toreturn wireless device 218. The directions may include a location tomail or ship wireless device 218. The directions may include a telephonenumber to call or other contact information in order to report findingwireless device 218 and to receive further instructions for returningwireless device 218 to its owner. In addition, the message may providean address in a display on the wireless device 218 and instructions todrop wireless device 218 in a mail box or take it to a deliveryprovider. In this way, the device may be returned to the owner (e.g.though a third party) in which wireless device 218's owner or the thirdparty or both may pay the cost for returning wireless device 218.

In addition, data recovery/purge application 224, in response toreceiving an alert request, may be configured to cause wireless device218 to emit an audible message on wireless device 218. Like theaforementioned audible alert and displayed message, the audible messagemay be pre-established on wireless device 218 prior to wireless device218 being alerted, provided to wireless device 218 when wireless device218 is alerted, or provided to wireless device 218 after the wirelessdevice is alerted. In other words, the audible message to be sounded inresponse to the alert request may be pre-established and pre-loaded intowireless device 218. In other embodiments, the audible message to besounded in response to the alert request may be received with the alertrequest or subsequent to receiving the alert request. The audiblemessage may comprise, for example, the same information as describedabove with respect to the aforementioned displayed message and could bepresented over a speaker on wireless device 218 as either a recordedaudio file or via text-to speech translation of a text message.

Also, data recovery/purge application 224, in response to receiving analert request, may be configured to cause wireless device 218 totransmit location information corresponding to a location of wirelessdevice 218. For example, the location information may comprise GPScoordinates of wireless device 218. In this way, if the owner ofwireless device 218 receives the GPS coordinates, the owner may be ableto go to those coordinates to recover lost wireless device 218. In otherembodiments, the GPS coordinates of wireless device 218 may be sent to aserver that may be configured to display to wireless device 218's ownera map indicating wireless device 218's location on the map based on theaforementioned GPS coordinates. The map may be presented to wirelessdevice 218's owner via a computer network, for example, the Internet.

Once alerted, wireless device 218 may be caused to be operable to call alimited number of telephone numbers. In addition, wireless device 218may be caused to indicate the limited number of telephone numbers. Thelimited number of telephone number may correspond to subjects or serviceproviders capable of providing information to wireless device 218'sfinder for returning wireless device 218. For example, wireless device218 may either audibly emit or visibly display a message stating “press1 to call this telephone's owner.” Furthermore, wireless device 218 mayeither audibly emit or display a message stating “press 2 to receivedata to help return this telephone to its owner.” The aforementioned areexamples, and other messages may be sounded or displayed by wirelessdevice 218 directed to help a subject finding wireless device 218 tocall one of the aforementioned limited number of telephone numbers. Itis noted that the presentation of this information may be in such a wayas to preserve the anonymity of the owner of the device. That is, whenthe subject finding wireless device 218 responds to the alert by, forexample, pressing “1” to call the owner of the device, the result isthat wireless device 218 invokes a telephony application, retrieves anumber to dial associated with the owner, and places a telephony callfrom wireless device 218 to the number retrieved, without requiring thedisplay, at any time, of the number being dialed or any otheridentifying information related to the owner of wireless device 218.Similarly, other types of communications can be used to send acommunication from wireless device 218 to a communication address forthe owner and may likewise maintain the anonymity of the owner ifdesired. These may include email, instant messaging, or any other typeof communication application supported by wireless device 218. Inenabling only specific addressable telephone numbers or other addresses,the utility of wireless device 218 may be limited to communication onlyfor the purpose of aiding in the return wireless device 218 to itsowner. All other communications may be disabled when this feature isinvoked. Any one or more of the aforementioned functions configured toindicate to a subject that wireless device 218 has been lost may beperformed alone or in combination with any other one or more of theaforementioned functions. The routine 400 then continues to operation485.

If the request data does not include a request to lock wireless device218, routine 400 continues to operation 485 where data recovery/purgeapplication 224 sends a return message to the invoking party. Inparticular, data recovery/purge application 224 may initiate and send ane-mail message from wireless device 218 over network 214 to the datarecovery address linked to invoking party in the database 226. Thereturn message may be sent to multiple addresses.

The return message may include the recovered data file as an attachmentand an acknowledgement confirming that data was recovered and/or purgedfrom wireless device 218. Consistent with embodiments of the invention,data recovery/purge application 224 may be configured to retry a datarecovery or purge request until successful. The return message may alsoinclude other information requested by the invoking party such as aconfirmation that wireless device 218 was locked or current locationinformation for wireless device 218. From operation 485, routine 400continues to operation 490, where it ends.

Generally, consistent with embodiments of the invention, program modulesmay include routines, programs, components, data structures, and othertypes of structures that may perform particular tasks or that mayimplement particular abstract data types. Moreover, embodiments of theinvention may be practiced with other computer system configurations,including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like. Embodiments of theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Furthermore, embodiments of the invention may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of the invention may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited tomechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the invention may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of the invention, for example, may be implemented as acomputer process (method), a computing system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier readable by acomputing system and encoding a computer program of instructions forexecuting a computer process. Accordingly, the present invention may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). In other words, embodiments of the presentinvention may take the form of a computer program product on acomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. Acomputer-usable or computer-readable medium may be any medium that cancontain, store, communicate, propagate, or transport the program for useby or in connection with the instruction execution system, apparatus, ordevice.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Embodiments of the present invention, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the invention. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While certain embodiments of the invention have been described, otherembodiments may exist. Furthermore, although embodiments of the presentinvention have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from theinvention.

All rights including copyrights in the code included herein are vestedin and the property of the Applicant. The Applicant retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

While the specification includes examples, the invention's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the invention.

1. A method for alerting a wireless device, the method comprising:receiving an alert request message; parsing the alert request messagefor request data; determining a type of alert being indicated by therequest data; and providing an alert performance message correspondingto the determined type to the wireless device.
 2. The method of claim 1,wherein providing the alert performance message comprises providing thealert performance message configured to cause the wireless device toperform a function configured to indicate to a subject that the wirelessdevice has been lost.
 3. The method of claim 1, wherein providing thealert performance message comprises providing the alert performancemessage configured to cause the wireless device to indicate a visiblealert.
 4. The method of claim 1, wherein providing the alert performancemessage comprises providing the alert performance message configured tocause the wireless device to indicate a visible alert, the visible alertcomprising at least one of the following: a light flashing sequence ofon/off time segments and a distinguishable light color.
 5. The method ofclaim 1, wherein providing the alert performance message comprisesproviding the alert performance message configured to cause the wirelessdevice to indicate an audible alert.
 6. The method of claim 1, whereinproviding the alert performance message comprises providing the alertperformance message configured to cause the wireless device to indicatean audible alert, the audible alert being one of the following:pre-established on the wireless device prior to providing the alertperformance message, provided to the wireless device when the wirelessis provided with the alert performance message, and provided to thewireless device after providing the alert performance message.
 7. Themethod of claim 1, wherein providing the alert performance messagecomprises providing the alert performance message configured to causethe wireless device to indicate an audible alert, the audible alertcomprising a motion alert produced by the wireless device.
 8. The methodof claim 1, wherein providing the alert performance message comprisesproviding the alert performance message configured to cause the wirelessdevice to displaying a message.
 9. The method of claim 1, whereinproviding the alert performance message comprises providing the alertperformance message configured to cause the wireless device todisplaying a message, the message being one of the following:pre-established on the wireless device prior to providing the alertperformance message, provided to the wireless device when the wirelessis provided with the alert performance message, and provided to thewireless device after providing the alert performance message.
 10. Themethod of claim 1, wherein providing the alert performance messagecomprises providing the alert performance message configured to causethe wireless device to provide an audible message.
 11. The method ofclaim 1, wherein providing the alert performance message comprisesproviding the alert performance message configured to cause the wirelessdevice to provide an audible message, the audible message being one ofthe following: pre-established on the wireless device prior to providingthe alert performance message, provided to the wireless device when thewireless is provided with the alert performance message, and provided tothe wireless device after providing the alert performance message. 12.The method of claim 1, wherein providing the alert performance messagecomprises providing the alert performance message configured to causethe wireless device to transmit location information corresponding to alocation of the wireless device.
 13. The method of claim 1, whereinproviding the alert performance message comprises providing the alertperformance message configured to cause the wireless device to beoperable to initiate a communication to a limited number ofcommunication addresses and to provide a prompt to initiate acommunication to at least one of the limited number of communicationaddresses.
 14. A method for alerting a wireless device, the methodcomprising receiving an alert performance message at the wirelessdevice, the alert performance message being configured to cause thewireless device to perform a function configured to indicate to asubject that the wireless device has been lost.
 15. The method of claim14, wherein receiving the alert performance message, the alertperformance message being configured to cause the wireless device toperform the function configured to indicate to the subject that thewireless device has been lost further comprises receiving the alertperformance message, the alert performance message being configured tocause the wireless device to perform the function configured to indicateto the subject that the wireless device has been lost wherein thefunction configured to indicate comprises the wireless device flashing alight on the wireless device based upon the received alert performancemessage.
 16. The method of claim 14, wherein receiving the alertperformance message, the alert performance message being configured tocause the wireless device to perform the function configured to indicateto the subject that the wireless device has been lost further comprisesreceiving the alert performance message, the alert performance messagebeing configured to cause the wireless device to perform the functionconfigured to indicate to the subject that the wireless device has beenlost wherein the function configured to indicate_comprises the wirelessdevice emitting an audible tone from the wireless device based upon thereceived alert performance message.
 17. The method of claim 14, whereinreceiving the alert performance message, the alert performance messagebeing configured to cause the wireless device to perform the functionconfigured to indicate to the subject that the wireless device has beenlost further comprises receiving the alert performance message, thealert performance message being configured to cause the wireless deviceto perform the function configured to indicate to the subject that thewireless device has been lost wherein the function configured toindicate comprises the wireless device displaying a message on thewireless device based upon the received alert performance message.
 18. Acomputer-readable medium which stores a set of instructions which whenexecuted performs a method for alerting a wireless device, the methodexecuted by the set of instructions comprising receiving an alertperformance message at the wireless device, the alert performancemessage being configured to cause the wireless device to perform afunction configured to indicate to a subject that the wireless devicehas been lost.
 19. The computer-readable medium of claim 18, whereinreceiving the alert performance message, the alert performance messagebeing configured to cause the wireless device to perform the functionconfigured to indicate to the subject that the wireless device has beenlost further comprises receiving the alert performance message, thealert performance message being configured to cause the wireless deviceto perform the function configured to indicate to the subject that thewireless device has been lost wherein the function configured toindicate comprises the wireless device flashing a light on the wirelessdevice based upon the received alert performance message.
 20. Thecomputer-readable medium of claim 18, wherein receiving the alertperformance message, the alert performance message being configured tocause the wireless device to perform the function configured to indicateto the subject that the wireless device has been lost further comprisesreceiving the alert performance message, the alert performance messagebeing configured to cause the wireless device to perform the functionconfigured to indicate to the subject that the wireless device has beenlost wherein the function configured to indicate comprises the wirelessdevice emitting an audible tone from the wireless device based upon thereceived alert performance message.